Method and system for improving efficiency of email forwarding by removing duplication

ABSTRACT

In a method and system for removing email forwarding duplication, when an email was sent for the first time, the email was assigned a unique identifier. An aggregate recipient list was created and associated with the unique identifier. When the email is to be forwarded, the aggregate recipient list has recipients previously forwarded the email. The recipient list of the forwarding email is compared with the aggregate recipient list. If duplicate email addresses are found, the duplicate email addresses are displayed to a sender of the forwarding email. If the sender chooses not to send the forwarding email to the duplicate email addresses, the duplicate email addresses are removed from the recipient list of the forwarding email. New recipients of the forwarding email are added to the aggregate recipient list. The forwarding email with the unique identifier is sent to the recipient list.

BACKGROUND OF THE INVENTION

Email has enabled businesses to improve communications and shareinformation. Used effectively, email can also help businesses to improveefficiency. Email systems have been enhanced in many ways to increasethe convenience and efficiency of its use. In current email systems,users can forward emails to an individual or a group of individuals toshare valuable information. However, multiple users may forward the sameemail to the same user. If a recipient's address happens to be in morethan one distribution group (or in both the original recipient list andthe forwarded group), the recipient will receive the same email multipletimes. The reading of duplicated messages lowers the efficiency for thereceiver.

Duplicate forwarded emails can be received in two ways: horizontalduplication and vertical/cyclic duplication. In horizontal duplication,multiple senders forward the same email to their respective distributiongroups, and their distribution groups overlap. For example, John is theproject manager for a project named Magic. Mary is the developmentmanager for Magic, so she includes John in her email distribution list.John reports to Robert, therefore John is also on Robert's distributionlist. There is a new development process in the company where John, Maryand Robert work. This new process is communicated to Robert and Marythrough identical emails sent by their managers. When Robert and Maryforward the emails from their managers to the people who work for them,John receives two emails with identical content from Robert and Maryregarding this new process.

In vertical duplication, a recipient belongs to more than onedistribution list along the email forwarding path. For example, John andMary are members of an architectural board, and John's manager isRobert. John receives an email with an overview of a new project, andforwards the email to the rest of the architectural board. Mary receivesJohn's email and forwards the email to Robert. Robert forwards the emailto his department, which includes John. John receives the forwardedemail he had forwarded himself.

BRIEF SUMMARY OF THE INVENTION

In a method and system for removing email forwarding duplication, whenan email was sent the first time, the email was assigned a uniqueidentifier. An aggregate recipient list was created and associated withthe unique identifier. The aggregate recipient list has recipientspreviously sent the email. when the email is to be forwarded, therecipient list of the forwarding email is compared with the aggregaterecipient list. If duplicate email addresses are found, the duplicateemail addresses are displayed to a sender of the forwarding email. Ifthe sender chooses not to send the forwarding email to the duplicateemail addresses, the duplicate email addresses are removed from therecipient list of the forwarding email. New recipients of the forwardingemail are added to the aggregate recipient list. The forwarding emailwith the unique identifier is sent to the recipient list.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE FIGURES

FIG. 1 illustrates an exemplary embodiment of a system for removingemail forwarding duplication.

FIG. 2 illustrates an exemplary embodiment of a method for removingemail forwarding duplication.

FIG. 3 illustrates in more detail the exemplary embodiment of a methodfor removing email forwarding duplication.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a method and system for removing emailforwarding duplication. The following description is presented to enableone of ordinary skill in the art to make and use the invention and isprovided in the context of a patent application and its requirements.Various modifications to the embodiment will be readily apparent tothose skilled in the art and the generic principles herein may beapplied to other embodiments. Thus, the present invention is notintended to be limited to the embodiment shown but is to be accorded thewidest scope consistent with the principles and features describedherein.

The method and system for removing email forwarding duplication assignunique identifiers (ID) to new emails, create an aggregate recipientlist to which the recipients of the email are added, associates theaggregate recipient list with the unique ID, and stores the unique IDand the aggregate recipient list. Each time the email is to beforwarded, the aggregated recipient list associated with the unique IDis retrieved, and the recipient list of the forwarding email is checkedfor duplicates against the aggregated recipient list. Duplicaterecipients can be removed from the recipient list of the forwardingemail. New recipients are added to the aggregated recipient list andstored. The forwarding email is then sent to the recipients, along withthe unique ID.

In an exemplary embodiment, the invention is implemented in software,which includes but is not limited to firmware, resident software,microcode, etc. The invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. For the purposes of this description,a computer-usable or computer readable medium can be any apparatus thatcan contain, store, communicate, propagate, or transport the program foruse by or in connection with the instruction execution system,apparatus, or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Current examples of opticaldisks include compact disk-read only memory (CD-ROM), compactdisk-read/write (CD-R/W) and DVD.

FIG. 1 illustrates an exemplary embodiment of a system for removingemail forwarding duplication. The system includes an email server 101for providing email service to a plurality of email clients 104-106. Theemail server 101 has access to a datastore 102, which stores unique IDsassigned to emails and their associated aggregated recipient lists 103,as described further below. In one exemplary embodiment, the datastore102 is an email database, but the datastore 102 can be any other type ofstorage mechanism without departing from the spirit and scope of theinvention.

FIG. 2 illustrates an exemplary embodiment of a method for removingemail forwarding duplication. Referring to both FIGS. 1 and 2, when anemail is sent for the first time, the email is assigned a unique ID. Anaggregate recipient list 103 is also created and associated with theunique ID (step 200). The recipients of the email are added to theaggregate recipient list 103. The aggregate recipient list 103 containsa history of recipients who have been sent the email assigned the sameunique ID. A user 107 receives the email assigned the unique ID (step201). When a user 107 decides to forward the email, the user 107instructs the email client 104 to create a forwarding email to send thereceived email to a recipient list (step 202). In this specification, a“forwarding email” forwards a copy of an email received from anotheruser to one or more recipients. Typically, the email client 104 createsthe forwarding email when the user 107 selects the “forward” button onhis email application.

The email client 104 compares the recipient list for the forwardingemail with the aggregate recipient list 103 associated with the uniqueID stored at the datastore 102 (step 203). The aggregate recipient list103 is retrieved from the datastore 102 so that the comparison can beperformed. From this comparison, duplicate recipients are identified.Alternatively, the comparison can be performed by the email server 101.Here, the email client 104 sends the forwarding email recipient list tothe email server 101 for the comparison, with the results of thecomparison sent to the email client 104 by the email server 101. Theemail client 104 can then remove duplicate recipients from the recipientlist of the forwarding email (step 204), while new recipients are addedto the aggregate recipient list 103 (step 205). The email client 104then sends the forwarding email with the unique ID to the recipient list(step 206).

Steps 201 through 206 are repeated each time the email is forwarded.When the original email was created, the unique ID was assigned to theemail and stored at the datastore 102. The forwarding emails maintainthe same unique ID throughout the email forwarding chain. The unique IDcan be sent as part of the header of the forwarding emails. An emailforwarding chain is a set of email forwarding steps, where in each step,the user who forwards the email does not add new information on top ofthe forwarded email, except for non-essential messages, such as “FYI”,“please read”, etc. A user can start a new email forwarding chain whenenough new content is added to a forwarding email. This forwarding emailis treated as a new email and assigned a new unique ID.

In the exemplary embodiment, the headers and bodies of the forwardedemails within the email forwarding chain are hidden by default, and abrief forwarding path is substituted. The brief forwarding path is usedto prevent distraction of the user when reading the original emailcontent. Optionally, a user can choose to display the full forwardingpath.

The parameters of the email forwarding duplication removal feature canbe configurable by a user. For example, a user can set an expirationperiod, after which the unique ID is no longer valid. Optionally, theunique ID can be set to automatically expire after a certain amount oftime after the last forwarding activity. Once the unique ID is no longervalid, the mapping of the aggregate recipient list to with the unique IDis cleared from the datastore 102.

The email forwarding chain can have many branches, as multiplerecipients of forwarded email can forward the same email to others. Foreach branch, the same unique ID is maintained and associated with asingle, global aggregate recipient list 103.

FIG. 3 illustrates in more detail the exemplary embodiment of a methodfor removing email forwarding duplication. When an email is sent for thefirst time (step 301), the email is assigned a unique ID (step 302). Anaggregate recipient list 103 is created, to which the recipients of theemail are added. The aggregate recipient list 103 is associated with theunique ID (step 303). The unique ID and the aggregate recipient list arestored at the datastore 102 (step 304). When a user 107 decides toforward the email (step 305), the email client 104 retrieves theaggregate recipient list 103 associated with the unique ID of the emailfrom the datastore 102 (step 306). The recipient list of the forwardingemail is checked against the aggregate recipient list 103 (step 307). Ifduplicate email addresses are identified (step 308), the duplicate emailaddresses are displayed to the sender of the forwarding email (step309). The sender can choose whether or not to send the forwarding emailto the duplicate email addresses. If the sender chooses not to send(step 310), the email client 104 removes the duplicate email addressesfrom the recipient list of the forwarding email (step 311). Any otherparameters for the email forwarding duplication removal feature can beconfigured by the user 107.

New recipients of the forwarding email are added to the aggregaterecipient list 103 by the email client 104 and stored in the datastore102 (step 312). The email client 104 sends the forwarding email with theunique ID to the recipient list (step 313). Steps 306 through 313 arerepeated each time the forwarding email is further forwarded.

Consider the horizontal distribution example set forth above, where Johnis the project manager for a project named Magic. Mary is thedevelopment manager for Magic, so she includes John in her emaildistribution list. John reports to Robert, therefore John is also onRobert's distribution list. There is a new development process in thecompany where John, Mary, and Robert work. Robert and Mary receiveidentical emails sent to them by their managers (step 301). The emailwas assigned a unique ID when the email was created (step 302). Theaggregate recipient list 103 was also created, associated with theunique ID, and stored at the datastore 102 (steps 303-304).

Robert then decides to forward the email to his distribution list, whichincludes John (step 305). The aggregate recipient list 103 associatedwith the unique ID of the email is retrieved from the datastore 102(step 306). The recipient list of Robert's forwarding email is checkedagainst the aggregate recipient list 103 (step 307). Assume that thischeck finds no duplicate email addresses (step 308). The recipients ofRobert's forwarding email are added to the aggregate recipient list 103and stored at the datastore 102 (step 312). Robert's forwarding emailwith the unique ID is then sent to the recipient list (step 313). Johnreceives the forwarded email from Robert.

Mary decides to forward the email to her distribution list, which alsoincludes John (step 305). The aggregate recipient list 103 associatedwith the unique ID of the email is retrieved from the datastore 102(step 306). The recipient list of Mary's forwarding email, whichincludes John, is checked against the aggregate recipient list 103 (step307). This check finds John's email address is a duplicate email address(step 308), and John's email address is displayed to Mary (step 309).Assume that Mary decides not to send the forwarding email to John (step310). John's email address is removed from the recipient list of Mary'sforwarding email (step 311). New recipients of the forwarding email areadded to the aggregate recipient list 103 and stored at the datastore102 (step 312). Mary's forwarding email with the unique ID is then sentto the recipient list (step 313), which does not include John. Thus,John does not receive duplicate forwarded emails.

Consider also the vertical distribution example set forth above, whereJohn and Mary are members of an architectural board, and Robert isJohn's manager. John is sent an email with an overview of a new project(step 301). The email was assigned a unique ID when the email wascreated (step 302). An aggregate recipient list 103 was also created,associated with the unique ID, and stored at the datastore 102 (step303-304).

John decides to forward the email to fellow board members (step 305).The aggregate recipient list 103 associated with the unique ID of theemail is retrieved from the datastore 102 (step 306). The recipient listof John's forwarding email, which includes Mary, is checked against theaggregate recipient list 103 (step 306). Assume that this check finds noduplicate email addresses (step 308). The recipients of John'sforwarding email are added to the aggregate recipient list 103 andstored at the datastore 102 (step 312). John's forwarding email with theunique ID is then sent to the recipient list (step 313). Mary receivesthe forwarded email from John.

Mary decides to forward John's email to Robert (step 305). The aggregaterecipient list 103 associated with the unique ID of the email isretrieved from the datastore 102 (step 306). The recipient list ofMary's forwarding email, which includes Robert, is checked against theaggregate recipient list 103 (step 307). Assume that no duplicate emailaddresses are found (step 308). New recipients of the forwarding emailare added to the aggregate recipient list 103 and stored at thedatastore 102 (step 312). Mary's forwarding email with the unique ID isthen sent to the recipient list (step 313). Robert receives theforwarded email from Mary.

Robert decides to forward the email from Mary to his department, whichincludes John (step 305). The aggregate recipient list 103 associatedwith the unique ID of the email is retrieved from the datastore 102(step 306). The recipient list of Robert's forwarding email, whichincludes John, is checked against the aggregate recipient list 103 (step307). This check finds John's email address is a duplicate email address(step 308), and John's email address is displayed to Robert (step 309).Assume that Robert decides not to send the forwarding email to John(step 310). John's email address is removed from the recipient list ofRobert's forwarding email (step 310). New recipients of the forwardingemail are added to the aggregate recipient list 103 and stored at thedatastore 102 (step 312). Robert's forwarding email with the unique IDis then sent to the recipient list (step 313), which does not includeJohn. Thus, John does not receive duplicate forwarded emails.

A method and system for removing email forwarding duplication have beendisclosed. In the method and system, when an email was sent for thefirst time, the email was assigned a unique identifier. An aggregaterecipient list was created and associated with the unique identifier.The aggregate recipient list has recipients previously sent the email.When the email is to be forwarded, the recipient list of the forwardingemail is compared with the aggregate recipient list. If duplicate emailaddresses are found, the duplicate email addresses are displayed to asender of the forwarding email. If the sender chooses not to send theforwarding email to the duplicate email addresses, the duplicate emailaddresses are removed from the recipient list of the forwarding email.New recipients of the forwarding email are added to the aggregaterecipient list. The forwarding email with the unique identifier is sentto the recipient list.

Although the present invention has been described in accordance with theembodiments shown, one of ordinary skill in the art will readilyrecognize that there could be variations to the embodiments and thosevariations would be within the spirit and scope of the presentinvention. Accordingly, many modifications may be made by one ofordinary skill in the art without departing from the spirit and scope ofthe appended claims.

1. A method for removing email forwarding duplication, comprising:creating a forwarding email to send an email to a recipient list, theemail assigned a unique identifier, wherein an aggregate recipient listis associated with the unique identifier, the aggregate recipient listcomprising recipients previously sent the email; comparing the recipientlist of the forwarding email with the aggregate recipient list; andremoving duplicate recipients from the recipient list of the forwardingemail.
 2. The method of claim 1, further comprising: adding newrecipients of the forwarding email to the aggregate recipient list. 3.The method of claim 2, further comprising: sending the forwarding emailwith the unique identifier to the recipient list.
 4. The method of claim1, further comprising: determining if the email is being sent for afirst time; if the email is being sent for the first time, assigning theunique identifier to the email, creating the aggregate recipient list,wherein recipients of the email are added to the aggregate recipientlist, associating the aggregate recipient list with the uniqueidentifier of the email, and storing the aggregate recipient list. 5.The method of claim 1, wherein the comparing comprises: retrieving theaggregate recipient list associated with the unique identifier of theemail; comparing the recipient list of the forwarding email with theaggregate recipient list; and if the duplicate email addresses arefound, displaying the duplicate email addresses to a sender of theforwarding email.
 6. The method of claim 5, wherein the removingcomprises: determining if the forwarding email is to be sent to theduplicate email addresses; and if the forwarding email is not to be sentto the duplicate email addresses, removing the duplicate email addressesfrom the recipient list of the forwarding email.
 7. A method forremoving email forwarding duplication, comprising: creating a forwardingemail to send an email to a recipient list, the email assigned a uniqueidentifier, wherein an aggregate recipient list is associated with theunique identifier, the aggregate recipient list comprising recipientspreviously sent the email; retrieving the aggregate recipient listassociated with the unique identifier of the email, comparing therecipient list of the forwarding email with the aggregate recipientlist, and if the duplicate email addresses are found, displaying theduplicate email addresses to a sender of the forwarding email,determining if the forwarding email is to be sent to the duplicate emailaddresses, and if the forwarding email is not to be sent to theduplicate email addresses, removing the duplicate email addresses fromthe recipient list of the forwarding email; adding new recipients of theforwarding email to the aggregate recipient list and storing theaggregate recipient list; and sending the forwarding email with theunique identifier to the recipient list.
 8. A system, comprising: adatastore, comprising a unique identifier for an email and an aggregaterecipient list associated with the unique identifier, the aggregaterecipient list comprising recipients previously sent the email; and anemail client, wherein the email client: creates a forwarding email tosend the email to a recipient list, retrieves the aggregate recipientlist associated with the unique identifier of the email from thedatastore, compares the recipient list of the forwarding email with theaggregate recipient list, removes duplicate recipients from therecipient list of the forwarding email, adds new recipients of theforwarding email to the aggregate recipient list and stores theaggregate recipient list at the datastore, and sends the forwardingemail with the unique identifier to the recipient list.
 9. The system ofclaim 8, wherein the email client further determines if the email isbeing sent for a first time, wherein if the email is being sent for thefirst time, the email client: assigns the unique identifier to theemail; creates the aggregate recipient list, wherein recipients of theemail are added to the aggregate recipient list; associates theaggregate recipient list with the unique identifier of the email; andstores the aggregate recipient list at the datastore.
 10. The system ofclaim 8, wherein the comparing by the email client comprises: comparingthe recipient list of the forwarding email with the aggregate recipientlist; and if the duplicate email addresses are found, displaying theduplicate email addresses to a sender of the forwarding email.
 11. Thesystem of claim 10, wherein the removing by the email client comprises:determining if the forwarding email is to be sent to the duplicate emailaddresses; and if the forwarding email is not to be sent to theduplicate email addresses, removing the duplicate email addresses fromthe recipient list of the forwarding email.
 12. A computer programproduct comprising a computer useable medium having a computer readableprogram, wherein the computer readable program when executed on acomputer causes the computer to: create a forwarding email to send anemail to a recipient list, the email assigned a unique identifier,wherein an aggregate recipient list is associated with the uniqueidentifier, the aggregate recipient list comprising recipientspreviously sent the email; compare the recipient list of the forwardingemail with the aggregate recipient list; and remove duplicate recipientsfrom the recipient list of the forwarding email.